Session Start: Fri Jun 17 00:00:00 2016 Session Ident: #glitchpc [00:00] * Now talking in #glitchpc
[00:00] * Topic is 'Welcome to #glitchpc chat. Profanity, trolls, and impersonation are not welcome here. Street1 has become a Silent Keyboard. http://www.legacy.com/obituaries/savannah/obituary.aspx?page=lifestory&pid=139870551'
[00:00] * Set by jacky on Tue Mar 02 18:03:23
[01:30]<@BC_Programming> So peeps wassup
[07:44] * Quantos (Quantos@mib-6DD75DA6.ed.shawcable.net) Quit (Quit: Leaving)
[07:47] * Quantos (Quantos@mib-6DD75DA6.ed.shawcable.net) has joined #glitchpc
[09:43] * pottsi (Mibbit@pottsi.staff.mibbit.net) Quit (Client exited)
[09:44] * pottsi (Mibbit@pottsi.staff.mibbit.net) has joined #glitchpc
[09:44] * ChanBotIX sets mode: +v pottsi
[14:55]<+camerongray> BC_Programming: Stuck on a train
[14:55]<+camerongray> It's fun
[14:55]<+camerongray> (not)
[14:55]<+camerongray> Completely made an arse of it so now on a massive detour and need to change train in the middle
[14:56]<+camerongray> And trying to work over a network connection with latency ranging from 60ms to 10 seconds randomly
[16:45]<@BC_Programming> I've actually never been on a train
[16:45]<@BC_Programming> They are less integral to our public transport than the UK I think
[16:56]<@BC_Programming> Also been struggling with some bullshit Group Policies one of our customers IT put in place
[16:57]<@BC_Programming> prevents any exe from running in %APPDATA% to prevent malware. Yeah maybe before you did that you could have checked since our software updater runs the installers from the temp folder
[16:59]<@BC_Programming> C:\ProgramData it is I suppose
[17:07]<+camerongray> Ahh, ouch!
[17:10]<@BC_Programming> It's been a mystery for like a month why this one system couldn't use our updater
[17:10]<@BC_Programming> it would get stuck on every item at the "Installing" step
[17:10]<@BC_Programming> so we finally do a webex- so I can see the issue in action
[17:11]<@BC_Programming> so I download it manually and run it and I get a group policy error
[17:11]<@BC_Programming> and suddenly it all makes sense
[17:11]<@BC_Programming> The fun part is they are the same IT company responsible for another customer who we're upgrading next week
[17:12]<@BC_Programming> And they only want to remove the policy "temporarily" because it's a "security issue" Doesn't matter how secure the system is if they can't use any of the software their company needs...
[17:13]<@BC_Programming> seems like a sort of strongarm IT approach but I suppose it would work if it wasn't for our meddling updater
[17:13]<@BC_Programming> (For the record we were there first)
[17:15]<@BC_Programming> And of course we have to say "we'll be working with your IT staff on this" not "we'll be providing paddles for you to rectify the issue with your IT staff through corporal means"
[18:07]<@BC_Programming> meanwhile, my K70 keyboard has arrived
[18:09]<@BC_Programming> hmm... I think I prefer the unicomp for typing still... at least as long as it continues to function
[20:44] * Heinz (Mibbit@7478CB1E.FFA8211A.6DE10760.IP) has joined #glitchpc
[20:45] * Heinz (Mibbit@7478CB1E.FFA8211A.6DE10760.IP) Quit (Quit: http://www.mibbit.com ajax IRC Client)